home *** CD-ROM | disk | FTP | other *** search
- Path: news.interpath.net!Andy
- From: andy@ciinc.com (Andy Barnhart)
- Newsgroups: comp.lang.c++,comp.os.ms-windows.programmer.tools.mfc
- Subject: Re: Best way to resume from an exception
- Date: Wed, 13 Mar 96 13:54:15 GMT
- Organization: Interpath -- Providing Internet access to North Carolina
- Message-ID: <4i6jm4$mmg@news.interpath.net>
- References: <4i1qr9$g15@nntp1.best.com>
- NNTP-Posting-Host: cii02.ciinc.com
- X-Newsreader: News Xpress 2.0 Beta #0
-
- In article <4i1qr9$g15@nntp1.best.com>, DrLaz@aol.com wrote:
- >OK, wizards, what do you-all think is the best way to pick up after an
- >exception from the point at which it was thrown? For example--
-
- We do try/catch blocks around UI actions, so if a user encounters
- a bug it's less disasterous. We pop up a message box asking that
- the developers be notified of the circumstances and offer a file SaveAs
- (when possible) and suggest exiting ASAP. We don't throw exceptions
- on purpose - if we encounter one it is considered a serious error. We
- do attempt to resume, but in all probability some memory has been
- allocated and will not be freed, and initialization of an object (a CView
- derived class, for example) may not be complete. The reason we resume
- is purely PR - the customer feels a lot better about the app if it comes
- back to life after hitting an exception and allows him to close "normally".
-
- -Andy
-